---
title: 'Args'
sidebar:
  order: 1
  title: Args
---

<YouTubeCallout id="0gOfS6K0x0E" title="Build better UIs with Storybook Args" />

A story is a component with a set of arguments that define how the component should render. “Args” are Storybook’s mechanism for defining those arguments in a single JavaScript object. Args can be used to dynamically change props, slots, styles, inputs, etc. It allows Storybook and its addons to live edit components. You *do not* need to modify your underlying component code to use args.

When an arg’s value changes, the component re-renders, allowing you to interact with components in Storybook’s UI via addons that affect args.

Learn how and why to write stories in [the introduction](./index.mdx). For details on how args work, read on.

## Args object

The `args` object can be defined at the [story](#story-args), [component](#component-args) and [global level](#global-args). It is a JSON serializable object composed of string keys with matching valid value types that can be passed into a component for your framework.

## Story args

<IfRenderer renderer="svelte">

  To define the args of a single story, use the `args` property in the `Story` component if you are using Svelte CSF with the native templating syntax, or use the `args` key on a CSF story file:

</IfRenderer>

<If notRenderer="svelte">

  To define the args of a single story, use the `args` CSF story key:

</If>

{/* prettier-ignore-start */}

<CodeSnippets path="button-story-with-args.md" />

{/* prettier-ignore-end */}

These args will only apply to the story for which they are attached, although you can [reuse](./build-pages-with-storybook.mdx#args-composition-for-presentational-screens) them via JavaScript object reuse:

{/* prettier-ignore-start */}

<CodeSnippets path="button-story-primary-long-name.md" />

{/* prettier-ignore-end */}

In the above example, we use the [object spread](https://developer.mozilla.org/en-US/docs/Web/JavaScript/Reference/Operators/Spread_syntax) feature of ES 2015.

## Component args

<IfRenderer renderer="svelte">

  You can also define args at the component level; they will apply to all the component's stories unless you overwrite them. To do so, use the `args` property in the `defineMeta` function of a Svelte CSF story file or via the `args` key on the default CSF export:

</IfRenderer>

<If notRenderer="svelte">

  You can also define args at the component level; they will apply to all the component's stories unless you overwrite them. To do so, use the `args` key on the `default` CSF export:

</If>

{/* prettier-ignore-start */}

<CodeSnippets path="button-story-component-args-primary.md" />

{/* prettier-ignore-end */}

## Global args

You can also define args at the global level; they will apply to every component's stories unless you overwrite them. To do so, define the `args` property in the default export of `preview.js|ts`:

{/* prettier-ignore-start */}

<CodeSnippets path="args-in-preview.md" />

{/* prettier-ignore-end */}

<Callout variant="info" icon="💡">
  For most uses of global args, [globals](../essentials/toolbars-and-globals.mdx) are a better tool for defining globally-applied settings, such as a theme. Using globals enables users to change the value with the toolbar menu.
</Callout>

## Args composition

You can separate the arguments to a story to compose in other stories. Here's how you can combine args for multiple stories of the same component.

{/* prettier-ignore-start */}

<CodeSnippets path="button-story-primary-composition.md" />

{/* prettier-ignore-end */}

<Callout variant="info" icon="💡">
  If you find yourself re-using the same args for most of a component's stories, you should consider using [component-level args](#component-args).
</Callout>

Args are useful when writing stories for composite components that are assembled from other components. Composite components often pass their arguments unchanged to their child components, and similarly, their stories can be compositions of their child components stories. With args, you can directly compose the arguments:

{/* prettier-ignore-start */}

<CodeSnippets path="page-story.md" />

{/* prettier-ignore-end */}

## Args can modify any aspect of your component

You can use args in your stories to configure the component's appearance, similar to what you would do in an application. For example, here's how you could use a `footer` arg to populate a child component:

{/* prettier-ignore-start */}

<CodeSnippets path="page-story-slots.md" />

{/* prettier-ignore-end */}

## Setting args through the URL

You can also override the set of initial args for the active story by adding an `args` query parameter to the URL. Typically, you would use [Controls](../essentials/controls.mdx) to handle this. For example, here's how you could set a `size` and `style` arg in the Storybook's URL:

```
?path=/story/avatar--default&args=style:rounded;size:100
```

As a safeguard against [XSS](https://owasp.org/www-community/attacks/xss/) attacks, the arg's keys and values provided in the URL are limited to alphanumeric characters, spaces, underscores, and dashes. Any other types will be ignored and removed from the URL, but you can still use them with the Controls panel and [within your story](#mapping-to-complex-arg-values).

The `args` param is always a set of `key: value` pairs delimited with a semicolon `;`. Values will be coerced (cast) to their respective `argTypes` (which may have been automatically inferred). Objects and arrays are supported. Special values `null` and `undefined` can be set by prefixing with a bang `!`. For example, `args=obj.key:val;arr[0]:one;arr[1]:two;nil:!null` will be interpreted as:

{/* prettier-ignore-start */}

<CodeSnippets path="storybook-args-url-params-converted.md" />

{/* prettier-ignore-end */}

Similarly, special formats are available for dates and colors. Date objects will be encoded as `!date(value)` with value represented as an ISO date string. Colors are encoded as `!hex(value)`, `!rgba(value)` or `!hsla(value)`. Note that rgb(a) and hsl(a) should not contain spaces or percentage signs in the URL.

Args specified through the URL will extend and override any default values of args set on the story.

<IfRenderer renderer="react">
  ## Setting args from within a story

  Interactive components often need to be controlled by their containing component or page to respond to events, modify their state and reflect those changes in the UI. For example, when a user toggles a switch component, the switch should be checked, and the arg shown in Storybook should reflect the change. To enable this, you can use the `useArgs` API exported by `storybook/preview-api`:

  {/* prettier-ignore-start */}

  <CodeSnippets path="page-story-args-within-story.md" />

  {/* prettier-ignore-end */}
</IfRenderer>

## Mapping to complex arg values

Complex values such as JSX elements cannot be serialized to the manager (e.g., the Controls panel) or synced with the URL. Arg values can be "mapped" from a simple string to a complex type using the `mapping` property in `argTypes` to work around this limitation. It works in any arg but makes the most sense when used with the `select` control type.

{/* prettier-ignore-start */}

<CodeSnippets path="arg-types-mapping.md" />

{/* prettier-ignore-end */}

Note that `mapping` does not have to be exhaustive. If the arg value is not a property of `mapping`, the value will be used directly. Keys in `mapping` always correspond to arg *values*, not their index in the `options` array.

<details>
  <summary>Using args in addons</summary>

  If you are [writing an addon](../addons/writing-addons.mdx) that wants to read or update args, use the `useArgs` hook exported by `storybook/manager-api`:

  {/* prettier-ignore-start */}

  <CodeSnippets path="args-usage-with-addons.md" />

  {/* prettier-ignore-end */}
</details>